Resolves #7273(FR-2827)

Stacked on #7272.

## Summary

Deployment tags shown in the deployment list table and the detail Overview card are now interactive. Activating a tag (mouse click or keyboard Enter/Space) navigates to the deployment list with that tag pre-applied as a filter, so a tag becomes a one-click pivot to "find all deployments tagged X."

The URL shape uses the existing `iContains` filter that the list page already understands:

```
/deployments?filter={"tags":{"iContains":"<tag>"}}
```

(URI-encoded in the actual link.) Activating a chip from the admin context routes to `/admin-deployments` instead so users stay within the admin list.

## Changes

- `react/src/components/DeploymentTagChips.tsx` *(new)* — fragment-based component (`DeploymentTagChips_metadata` on `ModelDeploymentMetadata`) that renders all tag chips for a deployment. Wraps antd `<Tag>` with `role="button"`, `tabIndex={0}`, and Enter/Space `onKeyDown`. Owns the filter-URL contract inline (`buildDeploymentTagFilterUrl`) and uses `useLocation()` to keep admin-context activations on `/admin-deployments`. `stopRowClick` prop opts into `e.stopPropagation()` for use inside the table row; `fallback` prop renders when there are no tags.
- `react/src/components/DeploymentList.tsx` — replaces the inline tag rendering with `<DeploymentTagChips metadataFrgmt={row.metadata} stopRowClick fallback={…} />`. Filter prop changed from `string` to `GraphQLFilter` object so callers no longer JSON-stringify.
- `react/src/components/DeploymentConfigurationSection.tsx` — replaces the inline tag rendering in the Overview "Tags" descriptions item with `<DeploymentTagChips metadataFrgmt={deployment?.metadata ?? null} fallback={renderFallback()} />`. Spreads `DeploymentTagChips_metadata` in the page query.
- `react/src/pages/DeploymentListPage.tsx` and `react/src/pages/AdminDeploymentListPage.tsx` — read `filter` as a `GraphQLFilter` object via `nuqs` `parseAsJson`, with a guard that falls back to `{}` for non-object payloads (null/array/primitive). Removes the page-local `parseFilter*` helpers.
- `packages/backend.ai-ui/src/components/BAIGraphQLPropertyFilter.tsx` — derive `conditions` from `value` instead of holding it in `useState`. Reassigns sequential ids (`cond-${i}`) on derive so React keys stay stable; the previous random-id-per-call approach would have unmounted every Tag on every render once `conditions` was no longer a state. This is the bug surfaced when an external prop change (URL-driven query state) updated `value` but the rendered tags stayed on the stale state.

## Verification

- `bash scripts/verify.sh`: Relay PASS, Lint PASS, Format PASS. Two pre-existing TypeScript failures (`packages/backend.ai-client/src/client.ts` implicit-any errors and `react/src/components/DeleteForeverVFolderModalV2.tsx` missing-`options` error) reproduce on the parent branch (PR #7272) without these changes — they are unrelated.
- Manual: clicking and Enter/Space-activating a tag in both the list and the detail page navigate to the filtered list URL, the table reloads with only matching deployments, and the rendered filter tags reflect the URL value across re-renders. Activating a tag from `/admin-deployments` stays within the admin list.

## Notes

- No backend changes — the `{ tags: { iContains: ... } }` filter shape is already handled by the list pages.
- Detail-side splits comma-joined tag strings before render (preserved behavior); each individual tag becomes its own clickable chip.
- The chip currently replaces the entire `filter` query param when activated. This matches the issue's "filter applied" requirement; merging with an already-applied filter is left as a future polish.